B-20654

Summary

Is there anything you would like reviewers to give additional scrutiny?

Adding the ability to store/save the generated 858s in the system and view them in the admin app

Verification Steps for the Author

These are to be checked by the author.

• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

• Has the branch been pulled in and checked out?
• Have the BL acceptance criteria been met for this change?
• Was the CircleCI build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

• Instructions for starting storybook
• Instructions for starting the MilMove application
• Instructions for running tests

How to test

1. Access the test harness scenarios and run 'MakeMoveReadyForEdi'
2. grab the payment request number from the payload
   
3. run go run ./cmd/generate-payment-request-edi/ --payment-request-number 9641-6802-1
4. see a new record in payment_request_edi_files for that payment_request_number and the edi should match what's showing in terminal output
5. access Admin app
6. select Payment Request Syncada Files link on left nav
7. click the row of payment request number from above
8. validate the edi string is the same from db and terminal output
   

Frontend

• There are no aXe warnings for UI.
• This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
• There are no new console errors in the browser devtools.
• There are no new console errors in the test output.
• If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
• This change meets the standards for Section 508 compliance.

Backend

• Code follows the guidelines for Logging.
• The requirements listed in Querying the Database Safely have been satisfied.

Database

Any new migrations/schema changes:

• Follows our guidelines for Zero-Downtime Deploys.
• Have been communicated to #g-database.
• Secure migrations have been tested following the instructions in our docs.

Screenshots